Official Helium Community
⸺ HIP-Archive ⸺ / hip-42-beacon-witness-ratio-witness-reward-limit
Tracking/discussion issue: https://github.com/helium/HIP/issues/303
1
1
6
3
1 2
1 1 1
1
1 2
2
1 2 3
1
3 3 (to the rollover) 
1
they did this and this isn’t the peoples network” 
2
3 1 1 3 2 1 1 1
♂️ 1 1
1 1 1 1
1 1 5 1 1 1 2 1
1 but in the end helium team decides after all,so I believe they will never do anything that is bad for their precious 
1 7 1 1 1
1 1 1 1 1
4
1 1
1 2
1 2
1
1
1 1 1 1 1 1 1
1 1 1 1 1
1 2
1 1 1 1 1 1 1 1
yet there hasn’t been a beacon in 6 days, even my 4g setups don’t perform that badly. 2 yet there hasn’t been a beacon in 6 days, even my 4g setups don’t perform that badly. 
1 1 1 2 
can’t read erlang yet so I’ll never know.
2
1
1 1 1 1 4 1 1 1
1 1 1 
2
1
2
1
1 1 1
1 1 
1 3 3
hotspots can be investigated by the community since bobcat and sensecap are closed source hotspots can be investigated by the community since bobcat and sensecap are closed source 1 1
1 2
thanks! I will read up when I can. Just have the babies atm
1
1
1
icon icon 
1
1
1 3 1 1 1
poc_interval however still not a guarantee of that interval. Since the challenger gets a list of all occupied hexes on the network and randomly picks one to target.
Current libp2p issues indeed have lead to degradation in regards to PoC however the purpose of this HIP should still exist. There’s built in wiggle room already to help in situations that are out of the operators hands. I think one may say it’s too generous as it’s currently written.
With the shift to light hotspots most of those p2p issues will disappear and it’ll become even more strict. But those who don’t setup correctly are still going to have issues. 
2 1 as a starting base 1 as a starting base but what i like to know is that everyone starts with the same chances in order to be able to witness♂️
6 2
1 4 1 1
1
1
this is said in total jest...I really want to get to the bottom of this] this is said in total jest...I really want to get to the bottom of this] 
this is said in total jest...I really want to get to the bottom of this] 1 this is said in total jest...I really want to get to the bottom of this] 
last_poc_challenge is tied to this action. Since you haven't created a challenge in such a long time you're technically not eligible for PoC (ie beacons). The question then lies, why? Usually you see challenges being created constantly with other activities flatlining. I've seen a miner_poc_statem loop before that prevents them from performing said actions which essentially boiled down to a sync issue.
TL;DR - You're going to need to do a diagnostics on the hotspot (local or remote) and check on the block sync status. The other thing is do a remote reboot of the hotspot and see if that'll "wake" it up.last_poc_challenge is tied to this action. Since you haven't created a challenge in such a long time you're technically not eligible for PoC (ie beacons). The question then lies, why? Usually you see challenges being created constantly with other activities flatlining. I've seen a miner_poc_statem loop before that prevents them from performing said actions which essentially boiled down to a sync issue.
TL;DR - You're going to need to do a diagnostics on the hotspot (local or remote) and check on the block sync status. The other thing is do a remote reboot of the hotspot and see if that'll "wake" it up. last_poc_challenge is used to determine eligibility to beacon. If his doesn’t create a challenge the blockchain assumes it’s inactive. Even if it’s witnessing. I can show you in the source code if you’d like last_poc_challenge is used to determine eligibility to beacon. If his doesn’t create a challenge the blockchain assumes it’s inactive. Even if it’s witnessing. I can show you in the source code if you’d like 112iv4sfrCB5euAw5raCGUPzWWGGCYD3dZkXFa3zhMky4dusJwFP right?112iv4sfrCB5euAw5raCGUPzWWGGCYD3dZkXFa3zhMky4dusJwFP right? listen_addrs just the challenger needs to know the challengee -- wow this sentence sounded better in my head.. it's a loop of sorts listen_addrs just the challenger needs to know the challengee -- wow this sentence sounded better in my head.. it's a loop of sorts ♂️"... if you followed it by another notification that "hey, seriously you're hotspot isn't beaconing, you should fix this for your neighbors". Most will see what work is needed and what rewards they would get and give their neighbors the finger in most cases. Since they are doing "ok" why should they bend over backwards for their unknown neighbors even though most of their rewards are coming from their neighbors. 4 1
1
1
1 1 1
1
1♂️♂️ 
1 2 1 1 
1
4 1
1 2
1
/jk 1
️
️ Temperature check voting is now open to gauge community interest in HIP 42-Beacon/Witness Ratio, authored by @Anthonyra .
HIP 42, if implemented, would regulate the number of witnesses a Hotspot is rewarded for based on the number of successful beacons. This rewards 2-way LoRaWAN coverage and as a secondary benefit offers to limit some gaming due to witness stuffing.
• Read the HIP: https://github.com/helium/HIP/blob/master/0042-beacon-witness-ratio-witness-reward-limit.md
• Vote at https://helium.vote/
poc_challenge_interval which is now set at 360 versus the 240... With that being said the theoretical max is now 4. poc_challenge_interval which is now set at 360 versus the 240... With that being said the theoretical max is now 4. 3 1
1 1
8 1 1 1 5 1 1 1 1 4 1 1 1 1WITH witnessed_list AS (
SELECT witness_address, COUNT(transmitter_address) as witnessed
FROM challenge_receipts_parsed
WHERE block > (select min(height) from blocks where timestamp > now() - INTERVAL '5 DAYS') and witness_address = {{address}}
GROUP BY witness_address
)
SELECT c.transmitter_name, c.transmitter_address, COUNT(DISTINCT c.witness_address) as witnesses, w.witnessed, (COUNT(DISTINCT c.witness_address) * 6 * 2) as limit, (COUNT(DISTINCT c.witness_address) * 6 / 5 * 2) as daily_limit, w.witnessed > (COUNT(DISTINCT c.witness_address) * 6 * 2) as limited
FROM challenge_receipts_parsed as c
INNER JOIN witnessed_list as w
ON c.transmitter_address = w.witness_address
WHERE block > (select min(height) from blocks where timestamp > now() - INTERVAL '5 DAYS') and transmitter_address = {{address}}
GROUP BY transmitter_name, transmitter_address, w.witnessed; 
1 1 4 1 This network is one big experiment though 
This network is one big experiment though 2
1
1 1 1 1 1 1
witness_limit_cap a daily limit? 1
2 1
1 1 1https://imgur.com/a/Mq0n7CP 
1
2
4 1 1 1
Bad day's every day
Bad day's every day 1
2
1
1 1 right? I mean... 18 ain't that much right? I mean... 18 ain't that much 1
1 1
1
3 4 1 just wanted to confirm because that'd stink if PoC issues cause rewards not to go to hotspots that are providing 2-way comms to devices
2 just wanted to confirm because that'd stink if PoC issues cause rewards not to go to hotspots that are providing 2-way comms to devices 1
1
Could it negatively impact owners of devices from particular manufacturers I guess is part of my question, with the recent rak issues all in all I support this, I just want to try to poke holes in it) 
2 
3 1 1
1 1 2 2 1 3
1 1
1
1 1
1 1
poc_challenge_interval and poc_per_hop_max_witnesses chain variables... the current #1 hotspot only see's 536 witness rewards per day right now and the #1 hotspot with beacon witnesses have 165 unique witnesses..
poc_challenge_interval and poc_per_hop_max_witnesses chain variables... the current #1 hotspot only see's 536 witness rewards per day right now and the #1 hotspot with beacon witnesses have 165 unique witnesses.. 1 1
1
1
7 3 1
1
1
1 
1
1
1 4 1 1 1 1 
1 1 1 1 1... I would dream to be able to earn 2HNT for a day... 3 1 1
1 1 ... however it's not limited. It witnessed 443 the last 5 days and it's limit is 832 1 ... however it's not limited. It witnessed 443 the last 5 days and it's limit is 832 1
1 1
8 1
1
2
♂️ 2 1 1
1 1 1
1 1 1 1 1 2
1 1
1poc_challenge_interval is 576 1
1
1 I'm also not sure how many you will get in a real life scenario and if that makes it worth the effort(due to risk of extra load on validators for example). 1 1 1
2
1 1
1 1
1 1 1
1 2 6 1
1 https://earth.google.com/web/search/53.56313424557791,9.974871178664946/
1 1 1 but it does take some work and effort to "fix" them if there is a problem nonetheless but it does take some work and effort to "fix" them if there is a problem nonetheless 
1 2
1 1
1 learned a lot 2 2
1 1 N + 1 => N 1 1 Right in line with what I was imagining Right in line with what I was imagining ) 1 1 1
2 2 1 1 2
2
1
1
Seems perhaps more cost effective to the operator if it could be done in a way that would provide:
1. Better 1-way communication while still providing adequate 2-way communication
2. Better 2-way communication (I'm honestly not informed enough to know if this is impossible for some reason) - I'd assume you could have a complex install that covers a very wide area
Seems perhaps more cost effective to the operator if it could be done in a way that would provide:
1. Better 1-way communication while still providing adequate 2-way communication
2. Better 2-way communication (I'm honestly not informed enough to know if this is impossible for some reason) - I'd assume you could have a complex install that covers a very wide area 1 was a great discussion was a great discussion 
1
1
conversation only arose as I was voicing concerns on how HIP42 would affect me (and others in my region) 1 1
1
1 1
3 1 2 1 2 1 3 1 1 3
1 1 1 1 1
1 1♂️ 2 1 1 2 3
2 2
noice kkk 1
1 1 1 1 1
1 
2 1 1 1 1 1 1
1
3
1 3
2
1
1 9 1
5 1 1
2
1
2 1
2 1 1 1 2
1 2
1 3 1
1 2 1 
♂️ 1
or 
or or that makes them such destinations for this apparent cheating?
or or that makes them such destinations for this apparent cheating? 1 3 1 1 1 1 1 2 3 3 2 1 1 1 1 1 5 1 1 1
1 2 2
1
2 4 3
1 5 4 1
1
3 1
3 1
1
1 1
6 2 1 1 3
2 2
1 1
1 5 2 2 
3
2
2
1
1 1
Family thinks I am nuts. LoL 2
1 1 shake hands mate
2 1 1 2 1
Reason: Posting NSFW Websites 2 1 2 1
1 1 1 1 1
1 4 1 1
2 1 2 1 1 1 1 1 1 1 1 2 1 1 1 1
1 1 1 1 1
1 1 1 1 1 1
1 1 
1 2 1 1 1 2 1 It gets rid of obvious parasites, eliminates some cheating like witness relays, but on the other side it has the potential (unrealized so far as the examples we have seen here turned out to be other issues) to negatively impact some hotspots. 2
14 9 2 6 1
5 2 1
. Higher altitude setups can help increase @Helium coverage and $HNT rewards.
See the full DIY flagpole installation guide by Gabriel Chaparro: https://t.co/vX5CSPj5Xc.
It gets rid of obvious parasites, eliminates some cheating like witness relays, but on the other side it has the potential (unrealized so far as the examples we have seen here turned out to be other issues) to negatively impact some hotspots. 3 1 1 2 1 1 3 2 1 1 1
4 based on the IP bloom filter in place and that it gets reset every poc_challenge_interval which is currently set at 360 blocks. On the other side, there isn't a minimum amount of beacons a day a hotspot is restricted by the network either. Meaning that we can only see what an average hotspot can expect to receive based on a network average which is currently 2.4 which is where the compensation factor comes from as stated in the HIP.
4 based on the IP bloom filter in place and that it gets reset every poc_challenge_interval which is currently set at 360 blocks. On the other side, there isn't a minimum amount of beacons a day a hotspot is restricted by the network either. Meaning that we can only see what an average hotspot can expect to receive based on a network average which is currently 2.4 which is where the compensation factor comes from as stated in the HIP. 1 1 1 1 1 1 1
1 1
1 1 1 2 1 1 3 1
8 2
1 hotspot 4 hnt Day
2 1
9
2
1
2 1
3 2 2 1 1 2
1 1 1 1 1 1 1 1 2
1 1 1 2 1 1 1 1 1
1 1
1
1 2 dude he's trying to keep it civil you're arguing that you should be allowed to pick a fight and then cry about it and not just block a dude♂️ 1
Unless I guess someone posted a cheater hotspot that was yours and I said it was clearly cheating? I suppose that's possible. dude he's trying to keep it civil you're arguing that you should be allowed to pick a fight and then cry about it and not just block a dude ♂️ 1 1 2 1
1
poc_challenge_interval the beaconer doesn't have control over requesting a beacon because of what you said with custom firmware. Also, if you know the MD5 checksum you could simply send that to the checksum service. It's open sourced so you could easily figure out the required MD5 checksum needed poc_challenge_interval the beaconer doesn't have control over requesting a beacon because of what you said with custom firmware. Also, if you know the MD5 checksum you could simply send that to the checksum service. It's open sourced so you could easily figure out the required MD5 checksum needed 1 1 1 3 2 3 2♂️ 1 1 1 1 1 1 1 1♂️♂️ ♂️ 1 2 1 1 1
You just don't get those kind of results with p2p issues. 1 1 1 1 1 1 1 1 1 most likely it doesn't 1 1 1♂️ 1 1 1 1 1 1 1 1 1 1 2 thank you 2
1 1 1 1
1 2 2 2 1 1 1 
) )
Hell, don't even get me started on "Master" and "Slave" hard drives.
Hell, don't even get me started on "Master" and "Slave" hard drives. 1 1 4
3 1 1 1 1 1 1 1
1 1 1 1 2 2 2 2 1 1 1 1 1 1 1 2 
1 1 1 1 1 1 1
poc_challenge_interval is how often your hotspot tries to create a challenge. There's multiple reasons why one might miss this window but it's a check performed every block so eventually it'll create a challenge after those many blocks. This however, isn't saying that your hotspot will beacon at this interval. "If you had two hotspots on the network and they both try to create challenges at this interval then they should also beacon at that interval." It's a proxy since there's no guaranteed minimum beacon number. There is however a max 4 that's based on an IP bloom filter and an average based on the data on chain 2.4 it "shows" the community the opposite of what HIP-42 intentions are...poc_challenge_interval is how often your hotspot tries to create a challenge. There's multiple reasons why one might miss this window but it's a check performed every block so eventually it'll create a challenge after those many blocks. This however, isn't saying that your hotspot will beacon at this interval. "If you had two hotspots on the network and they both try to create challenges at this interval then they should also beacon at that interval." It's a proxy since there's no guaranteed minimum beacon number. There is however a max 4 that's based on an IP bloom filter and an average based on the data on chain 2.4 1 1 
1
1 1 2
1 1 1 1 1 1 1 ♂️ 1 1 1 3
♂️♂️ 
poc_challenge_interval has changed…
1 1 5
1 1 
1 1
1 1
. I’m new to helium and just starting to get the hang of it. What is the portal used to vote for hips. Most people don’t look into these small letters and just think that plugging the miner is the end of the road. 1 3 1
3 1
1 2 4
2 3
1 1
2
#hip-42-beacon-witness-ratio-witness-reward-limit has been locked!